镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

Allow placing aliases in a separate file - #2

Merged
dwaring87 merged 1 commit into
dwaring87:masterfrom
hcoyote:master
Feb 11, 2018
Merged

dwaring87 merged 1 commit into
dwaring87:masterfrom
hcoyote:master

Conversation

@hcoyote

@hcoyote hcoyote commented Jan 22, 2018

Copy link
Copy Markdown

This PR allows placing aliases in a separate config file ($HOME/.rtm.aliases.json) so you have the option of independently storing those in source control. Putting the $HOME/.rtm.json into source control is challenging because it contains private access keys to the RTM account (and it's good security practice to not store keys in github), so you have to jump through hoops in order to save your aliases.

This is a simple work around for this, by having a second file read upon startup that loads in the aliases file after the default user config is loaded. There may be a better way, but this was the most straight forward.

…source control independent of the private user data (auth keys)
@dwaring87
dwaring87 merged commit 99f28d3 into dwaring87:master Feb 11, 2018
@dwaring87

Copy link
Copy Markdown
Owner

Thanks for suggesting this - it would be good to separate the storage of the user credentials and the RTM CLI configuration. I just renamed the extra config file to use ~/.rtm.config.json by default since it could be used to store other config properties in addition to the aliases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants